home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970626-19970929
/
000312_news@newsmaster….columbia.edu _Mon Sep 8 09:54:22 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
8KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id JAA22339
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 8 Sep 1997 09:54:22 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id JAA00825
for kermit.misc@watsun; Mon, 8 Sep 1997 09:54:21 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!jaltman
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MSDOS Kermit to Kermit/2 script conversion notes
Date: 8 Sep 1997 13:54:19 GMT
Organization: Columbia University
Lines: 168
Message-ID: <5v102b$cen$1@apakabar.cc.columbia.edu>
References: <TCPSMTP.17.9.8.2.15.0.2375661496.4677362@kincyb.com>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:7635
In article <TCPSMTP.17.9.8.2.15.0.2375661496.4677362@kincyb.com>,
<dallasii@kincyb.com> wrote:
:
: [I'm cross-posting this to several forums where I think it will be
: appropriate for discussion.
: I apologize to anyone who finds it inappropriate (or long winded).]
It is considered polite to cross-post by listing all of the newsgroups
in one copy of the post instead of sending separate posts to each
group. That way every group gets to see the responses.
: Some notes on converting command files from MS-DOS Kermit 3.14 to
: Kermit/2 (Kermit-95 (C-Kermit for Windows-95) for OS/2)
: (henceforth referred to as K2, K/2 or K2.EXE)
: I welcome any comments:
:
: 1) The OS/2 "EXTPROC" command seems to be the most underdocumented
: OS/2 command I've come across. Few of the BIG, THICK OS/2 books
: (henceforth referred to as BTOB's) had much on it. Almost nowhere
: was there a real working example of it.
: I expected it to be something similar to the UNIX
: "#!/full/path/specification/to/the/interpreter" feature for the
: first line of a script. Almost, but not quite.
: The documentation all said something to the effect of:
:
: EXTPROC <device>:\full\path\interpreter <parameters here>
That is the correct syntax for EXTPROC, but ...
: I *expected* to use something like:
:
: EXTPROC <device>:\full\path\k2.exe = %1 %2 %3 %4 %5 %6 %7 %8 %9
This is not the syntax for Kermit-95. K95 (and C-Kermit) requires that
the command file be the first parameter on the command line.
: on the first line of the procs to use them as OS/2 commands that
: would pass the parameters to the script previously used for
: MS-DOS Kermit into \&@[0] ... \&@[8].
:
: What I found was needed was:
:
: EXTPROC <device>:\full\path\k2.exe <device>:\full\path\to\the\script.cmd
That is almost correct.
Try just
EXTPROC K2.EXE
assuming that K2.EXE is in your PATH. Then it should work fine. OS/2
will expand the current .CMD file and use that as the first parameter,
and then the .CMD command line parameters will follow it.
You can then access the command line parameters using command line
argument array \&@[].
: A further example:
:
: file1 (ktest5.cmd):
: ************************************************************
: EXTPROC D:\K2\K2.EXE C:\USR\COMM\Ktest6.CMD
: ; A--Note
: ; LAFN login script
: ; DEL 30/01/97
: echo \&@[0] \&@[1] \&@[2] \&@[3] \&@[4] \&@[5] \&@[6]
: IF DEFINED \&@[3] ASSIGN \%1 \&@[3]
: IF DEFINED \&@[4] ASSIGN \%2 \&@[4]
: IF DEFINED \&@[5] ASSIGN \%3 \&@[5]
: echo \%1 \%2 \%3 \%4 \7 \7 \7 \7 \7 the input
: echo Ktest5!\13\10
: EXIT
: *****************************************************************
This runs Ktest6.cmd instead of Ktest5.cmd because you have hard coded
the first parameter passed to K95 to be ktest6.cmd.
: file2 (ktest6.cmd):
: ******************************************************************
: EXTPROC D:\K2\K2.EXE C:\USR\COMM\Ktest6.CMD
: ; LAFN login script
: ; DEL 30/01/97
: echo Suprise, you got Ktest6 instead!\13\10
: EXIT
: *******************************************************************
: Yes, I was suprised.
: EXTPROC seems to work as a comment most of the time, and
: under certain circumstances as non-returning branch.
In K95 EXTPROC is exactly equivalent to COMMENT. It is a alias.
: (one of the goals here is a command "lynx <password>" that will take
: me directly from the OS/2 command line to my LA FreeNet account
: with Lynx active on my screen.)
You could do that with regular .CMD and .KSC files and bypass the
EXTPROC procedures.
: 2) While functioning as a comment in K/2, and apparently in
: most versions of C-Kermit, EXTPROC required some bogus
: definition as a macro to minimize interuption when scripts
: were run back with MS-DOS Kermit, I think I just
: "define EXTPROC echo" in my MSCUSTOM.INI file to allow things
: to flow smoothly.
EXTPROC is not supported in DOS. Therefore, I do not believe that
anybody ever thought to add it there.
: 4) The GUI dialer works fine for targets where dialing in
: usually goes quickly with lots of open ports. With targets
: like a University mainframe on a Sunday afternoone, where
: everyone is trying to get their homework assignments finished,
: or my previous eMail provider, I found I needed scripts that
: would keep trying till they got through. Is there someway
: to set up the dialer so it will accept the userid/password
: as parameters, or ask you for them, without storing them,
: when invoked, then pass them to the dialup script.
: This may just be a point of my own ignorance about the Dialer & GUIs.
: I know it can be built into the scripts, but it seems like this
: should be just as much a part of the Dialer as the ability to
: store non-unique non-security issue passwords permenantly in the
: Dialer database.
The dialer provides for automatic retries. No scripting required.
This is built into K95's DIAL command. The number of retries,
interval between retries, etc are located on the Location->General
page.
If your host has multiple phone numbers you want to try use a Dialing
directory and specify the dialing directory entry name in the phone
number field instead of an actual phone number. K95 will auto-dial
through the entire list.
The dialer will not prompt for the password. However, you can specify
your own wrapper script that will prompt for the password and then
TAKE LOGIN.KSC to login. I will consider adding this feature.
: 5) I found I was frequently having to modify portions of the
: scripts to have a set of commands like:
:
: input <n> <some string>
: reinput 1 <the same string>
:
: It seems that when it's late at night, the target/host CPU has little
: to occupy it, and the not so busy phone lines allow a 28,800 connection
: maybe the prompts that the target are sending sneak through before interpreter
: on my feeble '386 is ready to respond, so it needs to recheck
: the received input to find something that was missed. When the host is
: busy and responds sluggishly, the phone lines are clogged and don't
: allow such fast connections the "input" command will catch the prompt
: itself. But this doesn't make any sense since everything must go through
: my CPU (the one running K/2) anyway, so why should it miss anything to begin
: with? Is this some sort of interupt/multi-threading issue, or am I just
: working to late on this to think clearly?
You will have to show us the script you are using to login in for us
to help you on this one. Of course, the usual things apply when using
high speed modems make sure that your flow control for the modem and
the serial port are set to Hardware Flow Control so that you do not
lose data and be sure to use a buffered UART such as a 16550.
Send support questions to kermit-support@columbia.edu.
Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
The Kermit Project * Columbia University
612 West 115th St #716 * New York, NY * 10025 * (212) 854-1344
http://www.columbia.edu/kermit/k95.html * kermit-support@columbia.edu